l4re: change bit widths of file offset types#5173
Conversation
a64dd66 to
66c2f42
Compare
66c2f42 to
244c00b
Compare
This comment has been minimized.
This comment has been minimized.
244c00b to
f0bf0bf
Compare
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
f0bf0bf to
caac209
Compare
This patch makes a few changes to the file offset types and routines that are made available under the `unix/linux_like/l4re` module. The current upstream definitions under x86_64 and AArch64 are unconditionally 64-bit. Then there's the fact there's only one target officially supported by rustc under L4Re, and that's x86_64.
caac209 to
e16db76
Compare
|
I'm pretty fine deprecating these since the platform has pretty low use, but we should figure out the other uclibc PR first. @SnoozeThis #5165 -> remove label S-blocked, add label S-waiting-on-review |
|
(https://snoozeth.is/u1Hjq3aITKU) I will wait until #5165 is merged and then add label S-waiting-on-review and remove label S-blocked. @rustbot claim. |
| #[deprecated( | ||
| since = "0.2.187", | ||
| note = "Use `fsblkcnt_t` instead. The unsuffixed type is defined in terms of the suffixed type \ | ||
| upstream under the current target architecture (x86_64,) and support for suffixed \ | ||
| types is phasing out in the `libc` crate." | ||
| )] | ||
| pub type fsblkcnt64_t = c_ulong; |
There was a problem hiding this comment.
The arch is wrong here but these deprecation messages are more complicated than needed anyway. Let's keep things simple and point elsewhere if more info is required, e.g.:
Use
fsblkcnt_tinstead. LFS64 aliases are being phased out, see #4805.
Description
This PR deprecates a number of symbols from the
unix/linux_like/l4remodule. This has also come with further deprecations and modifications in other top-level modules.At present, the definitions in upstream l4re-core are always 64-bit wide for the 64-bit targets we seem to support in this module. Though rustc only has support for x86_64 under this target OS.
Sources
Sources on the uClibc changes are documented in #5165. A regex search of the affected symbols on l4re-core's
libcdirectory reveals no modifications in their patches would necessitate changes in this patch.Checklist
libc-test/semverhave been updated*LASTor*MAXare included (see #3131)cd libc-test && cargo test --target mytarget); especially relevant for platforms that may not be checked in CI@rustbot label +stable-nominated